Dual Image Feature

The device has a dual image in its flash memory. The key purpose of this architecture is to support a fallback mechanism to prevent downtime that may arise because of firmware related-issues occurring during every day operations and during a firmware upgrade. The dual image architecture includes separate flash memory segments for the active firmware image, redundant firmware image and another image for system-related data including the device’s running configuration file. This mechanism is implemented for the following scenarios:

■

System Startup: Upon every successful system startup, the redundant .cmp file is checked, validated and restored if necessary (in case it’s corrupted or different to the active .cmp file).

■

Firmware Upgrade:

●

The new .cmp file is burnt to the active partition.

●

The device’s existing running configuration file is backed up to the system partition.

If during the firmware upgrade, one of the following occurs:

●

The upgrade process fails or the device doesn’t fully complete the boot process.

●

The device’s firmware is corrupted.

Then the device restores it’s backed up .cmp and running configuration files, thereby ensuring seamless operation.

If the upgrade process succeeds, the backed up files are deleted, the new .cmp file is copied to the redundant partition and the new running configuration file is backed up to the system partition.